home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 25
/
Cream of the Crop 25.iso
/
bbs
/
fdapx112.zip
/
SYSOP.TXT
< prev
Wrap
Text File
|
1997-03-26
|
4KB
|
102 lines
FrontDoor APX/w - Information to an operator of a server (boss) system
======================================================================
Copyright 1997 Mats Wallin; All rights reserved.
This document contains some information about FrontDoor APX/w for the
benefit of an operator of a server system that has, or is in the
progress of getting, one or more clients (points) that are using
FrontDoor APX/w.
This document attempts to address three main topics:
1) What information the client needs from the server operator to be
able to configure FrontDoor APX/w correctly.
2) How you can pre-configure an archive with FrontDoor APX with some
(or all) the configuration information, to make it easier for the
client to setup the software.
3) What FrontDoor APX/w requires of your system to work.
1) Information that a client needs to configure FrontDoor APX/w
---------------------------------------------------------------
FrontDoor APX/w is very easy to setup, and very few settings have to
be configured for a basic configuration. Actually, only the following
information is required:
* The address of the server (boss), i.e. your system.
* The address of the client (point), i.e. his system.
* The phone number he should dial when calling your system. The phone
number should be specified exactly as it is specified when it is
dialed on the phone.
The above is all information that always is required. But, it might
also be a good idea to setup a session level password. Btw, unless
otherwise configured, FrontDoor APX/w uses the session level password
as the packet password and the AreaFix password also.
You might also want to provide the client with a list of echomail
conferences that the user should be able to access.
That's about it.
2) Pre-configuring an archive with data about your system
---------------------------------------------------------
It is possible to create a pre-configured version of FrontDoor APX for
the clients of your server. You can either create a specific archive for
each client, that contains all information that is needed (including
the name of the client), or you can create an archive that is generic
for all your clients. If you do the later, the only thing the client
has to configure manually is his own name, the client address and the
session level password.
To pre-configure an archive with FrontDoor APX/w like this, follow
these steps:
* Unpack the distribution archive (FDAPX112.*).
* Edit the file SETUP.CFG that is included. It contains descriptions
of all settings that can be pre-configured, and how to do it.
* Create a new archive containing all the original files plus your
modified copy of SETUP.CFG.
* Give this new archive to those that want to be clients of your
system.
If you make the new archive available for download or file request,
please make sure that you clearly indicate that this is a
pre-configured copy, and only useful for clients of your system. (This
is very important so that someone in another town or country does not
download your modified copy by mistake.) If possible, try to use
another name than the original name, for the new archive.
3) Requirement of your system
-----------------------------
FrontDoor APX/w requires the following from a server system:
* An EMSI capable mailer
* Mail should be compressed with either ZIP, ARJ, ARC or PAK (or sent
uncompressed).
An AreaFix compatible program that processes messages to AreaFix is
not required, by FrontDoor APX/w will attempt to use it. The AreaFix
program should preferable support the FidoNet standard FSC-0057, which
is a proposed standard for AreaFix programs.
(It is possible to configure FrontDoor APX to send the AreaFix message
to another name than AreaFix, but it uses AreaFix by default).
// End of file "sysop.doc"